Usually not a fan of using cy.wait(), what is the reason for it in this case?

Usually not a fan of using cy.wait(), what is the reason for it in this case?

@elzody I understand but I suspect the click event hadn't been bound yet at some point. That's why I try adding a short delay before performing the click action.

... I suspect the click event hadn't been bound yet at some point.

Do you mean that the element was not visible yet and that the click event could not go through? Just a bit confused on what you mean by "hadn't been bound yet." I guess it's fine either way, just want to see if there is another way since this is considered an anti-pattern: https://docs.cypress.io/api/commands/wait#Time

@luka-nextcloud

@elzody Based on the Cypress report, we can see that the element is visible. However, when a click is performed, nothing happens. So, I suspect the click event listener on that element might not be ready yet.